home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
tccb109.zip
/
TCCB.DOC
< prev
next >
Wrap
Text File
|
1991-12-13
|
38KB
|
937 lines
- T C C B -
Ver 1.08
by
Paul Michaelson
&
Bruce Pinto
December 08, 1991
TCCB (C) 1991 a BBS Call Back Registration Program Version 1.08
Users Manual
By Paul Michaelson 12-08-91 07:35pm
TCCB is a copyrighted software product designed by Paul Michaelson
and written by Paul Michaelson and Bruce Pinto. TCCB or any part of
the TCCB distribution package may not be distributed in any fashion
without prior written permission from the authors. TCCB is NOT in the
public domain.
Limited license is granted to distribute the SHAREWARE version of
TCCB. SYSOPS: You may include the shareware version of TCCB in your
file directories for downloading to the general public. Shareware
distributors may distribute the Shareware versions of TCCB as long as
the program is NOT sold. A small charge may be made to recover media
costs only. Registered copies of TCCB may not be distributed for any
reason. You may use the unregistered version of TCCB for 30 days to
evaluate the program. After 30 days from the time you started using
TCCB you must register it, or stop using it.
Where to get a copy of TCCB
---------------------------
The main distribution sites for TCCB are the authors BBS in
northern Virginia, and the main beta test site in Rome New York.
These system are:
Author's BBS: Main BETA test site:
Frostbyte Falls BBS Ulysses Systems Network
SysOp: Paul Michaelson SysOp: Joseph Aquino
Phone 703-425-6640 BBS Node #1 - (315) 339-5591 HST v.32b v.42b
24 Hrs. 3/12/24 Node #2 - (315) 339-5595 HST v.42b
File requests honored 24-Hrs other than NMH
RBBSNET: 8:954/401 & 8:954/402
FIDONET: 1:260/501 & 1:260/502
EGGNET: 99:9226/501
Use MAGIC File Name: TCCB for the latest
version of the "TCCB" Callback door.
Disclaimer of Warranty
----------------------
No warranty of any kind is offered with TCCB either stated or
implied. You must use the program at your own risk. TCCB (including
the instructions for it's use) is provided "AS IS" without warranty of
any kind. The authors of TCCB do not warrant, guarantee, or make ANY
representations regarding the use, or results of the use, of TCCB or
any written materials concerning TCCB in terms of correctness,
accuracy, reliability or otherwise. THE ENTIRE RISK AS TO THE RESULTS
AND PERFORMANCE OF TCCB IS ASSUMED BY YOU AND NOT THE AUTHORS OF TCCB.
If TCCB or it's written materials are defective, YOU, and not the
authors of TCCB, assume the entire cost of all necessary servicing,
repair, or correction.
Neither Paul Michaelson or Bruce Pinto (the authors of TCCB) shall
be liable for any special, direct, indirect, consequential or
incidental damages (including damages for loss of business profits,
business interruption, loss of business information, and the like)
arising out of the use or inability to use TCCB even if the authors
have been advised of the possibility of such damages.
Registering TCCB
----------------
TCCB is free to any RBBS system that does not charge for access.
If you run an RBBS and charge for access you must register the program
and pay for it. A BBS that charges for access is defined as: Any BBS
that receives payment for access to features (including more connection
time) that are not available to non paying users. It does NOT matter if
this payment is called a donation. If your users have to pay or make a
donation to get access to features that are not available to non paying
(donating) users then you are NOT running a free BBS. If you run an
RBBS that does NOT charge for access then you may use the program free
of charge but you still must register it. Donations will be accepted
in fact we are depending on them. If you are going to use the program
for free on a free RBBS then please consider a donation. Your donation
will make it possible for us to support this program and write new hi
performance C based programs for RBBS and other BBSs. A registration
form is included with the program. Fill out the registration form and
mail it to the address printed at the top of the form. If you are
paying to register TCCB or sending a donation you must send a check or
money order payable to "Paul Michaelson". If you register TCCB as a
free RBBS and at some time after registering begin to charge for access
you must cease to use the program or register again and pay for it.
Upon receipt of your completed registration form we will either send
you a registered copy of the program on disk (for paid registrations
only) or set up an account for you on Frostbyte Falls BBS the home of
TCCB. Accounts on FFBBS for free registrations require a three week
waiting period to set up. This allows us time to verify the information
you provided on the registration form. The authors reserve the right
to deny free registration to any BBS that we determine to not fit
the definition of a free access BBS. All decisions are final. Once
your FFBBS account has been set up, you will be allowed to download
your registered copy of the program from FFBBS. If you are sending in
a free registration, make sure to include the password you wish to use
on FFBBS. Future upgrades of TCCB for RBBS are free to registered
users. Registering SysOps receive full visiting SysOp privileges on
FFBBS as well as access to the TCCB conference.
NOTICE: The authors of TCCB reserve the right to abolish free
registrations, and revoke existing free registrations at any time. We
are hoping enough people will make donations to allow us to maintain
the program. If enough people make donations, we will continue to
allow free registrations. If very few people donate, we will be forced
to revoke free registrations, and charge everyone for the license to
use TCCB. PLEASE HELP TO SUPPORT FREE RBBS SYSTEMS AND DONATE WHAT YOU
CAN. EVEN A SMALL DONATION WILL GO A LONG WAY!
Description
-----------
TCCB is a program designed to run under a BBS and provide a way of
verifying the identity of new callers. TCCB is designed to run under
RBBS. Some of TCCB's features are:
- Sets user level after successful verification to level set by
the SysOp. The door can be configured to increase or decrease
the security level, or set it to a specific level. In fact
with the security level configuration file you can specify
that a user with any security level be set to a specified
security level if he/she is verified by the door, or another
level if the verification process fails!
- Will "SKIP" callback on user depending on users security
level. The sysop can define a range of security levels to be
verified. The door will "SKIP" (just return to the BBS) users
with security levels higher than the upper limit of this
range.
- Handles long distance calls. Configurable to callback or skip
long distance callers. Area Code configuration file permits
callback of selected area codes only at predefined times! You
can even allow a user to continue on the BBS or hangup after
he/she has been verified on a long distance callback.
- Local exchanges that require area codes to be sent are
supported.
- Fully logs each call with two log files. Optionally sends
main log to printer.
- Checks the users phone number against the log of verified
phone numbers to prevent multiple registrations.
- Works great on RBBSs with multiple nodes. All possible nodes
are fully supported.
- Instructions printed to user are simple text files allowing
SysOps to easily modify and customize them. Make the door
look any way you like!
- Supports ANSI graphics. One set of files for standard ASCII
output and another set of files for ANSI output.
- Automatically detects users graphics setting and prints the
appropriate text or ANSI graphics files.
- Supports Fossil Drivers.
- Supports 16550's with fifoed I/O.
- Serial I/O tested at speeds in excess of 115k baud.
- Desqview and network (LAN) compatable.
- Written in Borland Turbo C 2.0.
- Support available via author's RBBS for registered users.
- Free to RBBSs that do not charge for access or services.
- Register only once. No cost re-registration for new
RBBS versions (for payed registrations only).
- User friendly with simple instructions and no random numbers
to write down and type in 4 or 5 times. The program simply
asks the user to type his name to verify a connection.
- SAFE to use. Requires only the DORINFO[node#].DEF file to
operate. Poses no danger to your main users file because
it does NOT access it.
INSTALLING TCCB
---------------
To install TCCB unpack the distribution compressed file into your
RBBS main directory. This is the same directory you have the RBBS-
PC.EXE file in. Next create the BATCH file called by RBBS to run the
program.
NOTE: A program that will build a batch file for you automatically,
"INSTALL.COM", is included in the distribution package. The INSTALL
program is described later in this text.
TCCB is a standard RBBS door program, and interfaces to the BBS in
the same fashion as any door program. You must supply the complete
path and filename of the RBBS DORINFO[node#].DEF and DOUT[node#].DEF
files. You must supply the port information to tell the door which
communications port to use. Except for the security level, and area
code info, all configuration information is contained in the batch file
that invokes CB.EXE (the TCCB executable). The configuration
information is simply passed to TCCB as command line parameters when
the door is executed. This makes TCCB highly configurable. In fact on
a multinode system the door can be easily configured to use different
configurations for each node! An example batch file is shown below.
cb c:\rbbs\dorinfo1.def 5 02f8:3 c:\rbbs\dout1.def <continued>
ATZ ATX4V1Q0 ATDT BUSY "CONNECT" " " 10
<This is all one line>
The batch file requires just one line. The line consists of the
command to execute CB.EXE (the door program itself) and eleven or
twelve parameters. The parameters must be in the order shown and they
MUST be separated by spaces. They are:
NOTE: Some of these parameters are shown with double quotes. The
use of double quotes is only necessary if the parameter contains
spaces.
1. The complete path and filename including node
number of the RBBS DORINFO[node#].DEF file. For multi node
use make one batch file for each node. Make sure to set the
node number in this and the DOUT[node#].DEF file to the same
value.
NOTE: This file is created by RBBS when exiting to a door.
2. The DEFAULT security level given to the caller after
successfully completing the call back process. This is used
only if the security level configuration file does not exist,
OR the security level of the user has no corresponding entry
in the security level configuration file. This can be just a
number, or a number with a plus sign "+" or minus sign "-".
If this parameter is set to a simple number then the door
will set the users security level to this number after
verifying the user. If the number has a "+" plus sign in
front of it, then the door will add this number to the users
security level. If the number has a minus sign in front of
it, the door will subtract this number from the users
security level.
3 . The port address and IRQ number, separated by a colon, or for
Fossil Drivers the string "F:" followed by the port number.
Example: Standard ports: 02F8:3 for standard COM2
Fossil driver: F:2 for FOSSIL on COM2
NOTE: These port numbers are counting from 1.
Fossils count from 0 so if you list fossil STATUS it
will list COM2 as FOSSIL port 1! Read the Fossil
documentation for more information.
NOTE: It is recommended that you use a large buffer at least 1k
when the door is driving the serial port via a Fossil. If you have
memory to spare, use a 2k or larger buffer for the output buffer.
See the Fossil docs for info on command line parameters to set the
buffer size.
4. The complete path and filename of the RBBS DOUT[node#].DEF
file.
NOTE: This file is created by TCCB when TCCB exits to RBBS.
5. The string to send to your modem to get it to perform a
reset.
NOTE: This is usually "ATZ".
6. The string to send to your modem to configure it. This must
set up the modem to return the result codes ("CALL PROGRESS"
strings) that you specified in TCCB parameters 8 (BUSY) and 9
(CONNECT) as explained in this text. The example shown has
the modem configured to return word result codes. Numeric
result codes may also be used. It does not matter as long as
the modem returns the same strings as specified in the batch
file configuration parameters 8 and 9.
NOTE: Use "ATX4V1Q0" if unsure.
7. The dial command for your modem.
NOTE: Usually "ATDT" for touch tone or "ATD" for pulse dialing.
8. The string(s) your modem sends when a call should be aborted
and re-dialed. This can be a mix of several strings, like
"BUSYNO DIALTONE", with no delimiters required. You might
include any string returned by your modem that should trigger
an abort and re-try of the call in progress. Some modems
return "VOICE", "NO CARRIER", "ERROR", and other strings.
It is entirely up to you which conditions should trigger a
re-try. If the modem returns one of these strings after
dialing, the door will abort the call in progress, reset
the modem and dial the number again up to 3 times before
giving up. In most cases "BUSY" alone will do just fine.
NOTE: Usually "BUSY". If you wish to use a string containing
spaces, you must put double quotes around the string in the
batch file.
9. The string your modem sends when it has made a connection.
NOTE: Usually "CONNECT". If you wish to use a string containing
one or more spaces, you must put double quotes around the
string.
Example: "CONNECT 2400"
10. Long distance prefix. String to send before sending the area
code to accomplish a long distance call. Used when returning
long distance calls. If this is set to a blank (a SPACE, or
" ") character then the door will not make long distance
calls. To set to blank, use double quotes with ONE space, "
" , character inside. This can be many characters, but if it
contains spaces it must be inside double quotes, "like this".
NOTE: Usually a "1".
11. Lowest skipped security level. A user is skipped (just
returned to the BBS without being called back or verified) if
his/her security level is equal to or greater then this
number. If you want all security levels to be verified then
set this to a number higher then the highest level attainable
by your users. When a user is skipped the door will assign
the (F)ail security level in the security level configuration
file if it exists.
*12. Printer port. The printer is activated if this is a number
other then "0" zero. Enter 1 for LPT1, 2 for LPT2, and so
on... If this parameter is absent or "0" then the printer
will be turned off.
*This is optional and may be left out of the command line.
A "Standardized" version of the batch file is included with this
package. This file is configured as node #1, comm port COM2:, standard
RBBS paths, NO long distance calls returned, levels above 9 are
skipped. The modem strings are for a standard Hayes compatible modem.
The printer port parameter is "0" therefore the printer is turned off.
This file will work on most RBBS systems with just a few changes.
Once you have unpacked the compressed file, created your batch
file(s), and edited the .TXT/ANS and CFG files, you are done setting up
the door. Now run the RBBS utility "CONFIG" to set the path and name
of your batch file (CALLBAK.BAT) using CONFIG option #107 (RBBS 17.3c).
Next set the CONFIG option 108# to the highest security level to be
processed by the door ON EVERY CALL. This ensures that a caller that
fails to be verified on the first call will trigger the verification
process on every call until his/her security level gets raised
(presumably by the door) to a level higher then option #108. Make sure
that the security level that the door assigns to a verified user is
higher then this or RBBS will run the door every time a user calls!
That's it you are done, TCCB is installed! NOW TEST YOUR INSTALLATION.
Have someone call and test every aspect of the doors operation
including long distance operation. REMEMBER: Don't forget to set up
the area codes file or disable long distance call-backs by entering a
space as the long distance dialing prefix in the batch file!
The INSTALL utility for TCCB
----------------------------
To make installation of TCCB as painless as possible, a TCCB
batch file creation utility has been included in the distribution
package. The program "INSTALL.COM", will make a new batch file for
first time installation or modify an existing one. INSTALL can be used
to modify an existing batch file even if it contains many lines of
commands. INSTALL will search the file to find the line that runs TCCB
and configures it. If you have created multinode batch files to run
TCCB on a multinode RBBS you can use INSTALL to modify your batch
files. INSTALL must be run in the same directory where the batch file
exists. Install looks for a file with the name "CALLBAK.BAT" and uses
it. If it does not find the file then it will create a new one. After
invoking INSTALL from the dos prompt, the program will display a list
of 12 parameters. If INSTALL is modifying an existing file it will
display the current parameters after each entry. Simply enter or modify
each parameter until all 12 parameters are correct for your
installation. Enter a zero, "0", to exit the program. INSTALL will
then offer to write the changes out or just exit without saving any
changes. Be sure to set up RBBS for a callback door by setting the
RBBS "CONFIG" program options #107 and #108.
Files Used By TCCB
------------------
Included with the package are seven text (.TXT) files, two log
(.LOG) files, and seven ANSI type (.ANS) files. The two .LOG files are
the records of calls processed by the door. TCCB.LOG is a log of ALL
calls processed by the door successful or not. VERIFIED.LOG is a log
of just the successfully verified calls. This is the file used by the
door to detect and reject multiple registrations on one phone number.
The .TXT and .ANS files are printed to the user during the operation of
the door, and should be edited by the SysOp to customize them. Except
for a few specific places, the door uses these text files for ALL
output to the user. This makes TCCB a completely configurable callback
door. The .ANS files should contain ANSI graphics. The .TXT files
should contain ONLY pure ASCII text. The door will automatically
detect the users configuration and print the appropriate .TXT or .ANS
files. If the user has graphics turned on in the BBS then the door
will use the graphics (.ANS) files. Otherwise it will print the .TXT
files. The door will provide "MORE" processing on text (.TXT) files.
"MORE" processing is automatically turned off when in graphics mode.
The door can be used with the files just as they are, but I am sure you
can improve on them. At least put the name of your BBS in
CBINST.TXT/ANS, the opening instructions. The names and contents of
the .TXT/ANS files are as follows:
- CBINST.TXT/ANS Contains the opening instructions.
- CBINS1.TXT/ANS Contains instructions printed just before
hanging up.
- CBGUDNUM.TXT/ANS Printed when a user has been verified and
before returning to the BBS.
- CBDUPNUM.TXT/ANS Printed when a user is being rejected for
attempting to register a previously verified
number.
- CBBDNM.TXT/ANS Printed when the user fails to correctly
enter his/her FULL name after being called
back.
- CBNOVFY.TXT/ANS Printed when a users security level is equal
to or greater then the "SKIP" user level and
the door will just return to the BBS without
performing a call back.
- CBNOLD.TXT/ANS Printed to Long Distance callers when the
door is configured to refuse to call back
long distance, the users area code is not in
the configuration file, or there is a time
limit that is not satisfied for the callers
area code.
The first of the two .LOG files is TCCB.LOG, the main log of all
calls processed by the door. The second .LOG file is VERIFIED.LOG, this
file contains ONLY numbers that have been successfully verified. You
can start out with these files empty or if you are upgrading from
another RBBS callback door you can just copy the old log files from the
other door into the TCCB log files. It does not matter where the phone
number appears on the line as long as there is just one phone number
per line and each line is no more then 80 characters long. TCCB will
search the line to find the number. The phone number must be formatted
with minus sign characters separating the area code and exchange from
the body number (last four digits): XXX-XXX-XXXX
In addition to the .LOG and .TXT/ANS files there is the area code
configuration file called "CBAREACD.CFG". If this file exists then the
area codes contained in this file are the only area codes that the door
will call back and only at preset times! This feature of TCCB allows
the sysop to verify (RETURN) only those long distance calls that are
within a certain geographical area and only at a time when the long
distance tolls are favorable. It also allows the sysop to configure the
door to hang up after a long distance callback or allow the user to
remain online. Each area code has it's own set of time and hangup
control commands. If the file does not exist then the selective
callback feature is disabled, and the door will return calls to ANY
area code! NO error will be returned if the CFG file does not exist!
If you wish to use this feature then you must make sure that the file
is there. (NOTE: If you wish to disable ALL long distance call-backs,
you simply put a space contained in double quotes in place of the long
distance dialing prefix in the batch file.) The structure of the file
is free form, except that there is just one area code to each line with
one beginning time, one ending time, and one hangup control command.
The area codes, times, and hangup command may appear anywhere on the
line and be in any order. There must be no other information in the
file. Each line must be no more then 80 characters long. The area
code times and hangup commands are identified by a flag character just
before the area code, time entry, or hangup command. This flag
character may be in upper or lower case. The times are just the hours
in 24 hour format. The hangup command is a zero or non zero number.
If nonzero the door will hangup after completing the verification
process. The flag character for area code is "A", therefore the area
code "703" would appear as "A703" in the area code configuration file.
The flag characters for the beginning and ending times are "B" and "E"
respectively. The flag character for the hangup command is "H". Here
is an example line:
A909 E06 B14 H01
This line tells the door that it may call back area code 909, but only
between the hours of 2:00 o'clock pm and 6:00 o'clock am and that it
should hang up after the user has completed the verification process.
As you can see the entry for 6:00 o'clock am is "E06" NOT "E6". The
reason for this is that the door expects to find an hours spec in 24
hour (military) format, which is TWO numbers. The hangup command is
simply an "H" with a zero or non zero number after it. If the number
following the hangup command is non zero then the door will hang up
after a long distance callback to the area code on that line. The area
code, times, and hangup command must be separated by spaces.
Local Area Code Configuration
In addition to the long distance area codes in the area code
configuration file, there is a provision for calling local phone
numbers that require an area code sent in addition to the main number.
If your dialing area does not require area codes to make a local call
then you can ignore this feature. To set up the area code file to send
the area code for a given local call, you must add the local area code
to the configuration file but use "L" for the flag character instead of
"A" for long distance area codes. An example line for local area code
909 is given below:
L909
This line tells the door to dial the area code on a local call to area
code 909. You may combine local and long distance area codes on the
same line as long as there is just one local and one long distance
area code on each line. If you have more then one local or long
distance area code on a line then the door will ignore all but the
first one. If you have local and long distance calls going to area
code 909 you can make an entry like this:
A909 L909 B14 E06 H01
This line tells the door to send the area code on local calls to area
code 909, and allow long distance callbacks to area code 909 if the
call will take place between the times of 2:00 o'clock pm and 6:00
o'clock am, and then to hang up after the callback.
An example CFG file is provided with the package. MAKE SURE TO
EDIT OR DELETE THIS FILE! Otherwise the door will return calls only to
the area codes in the example file! If you enter a quoted space where
the long distance dialing prefix goes in the batch file then the door
will NOT return long distance calls and will ignore the area code
configuration file.
Security Level Configuration File
---------------------------------
A new feature as of version 1.05 is the addition of a security
level configuration file. This file (if it exists) controls the
security level given to the user when the user exits from the door.
This means that it even sets the users security level when the user
fails to complete the verification process. The levels that the user
gets are defined in the configuration file. There are three entries each
with a flag character just like the area code configuration file.
The flag characters are "E" for the users security level when she/he
enters the door, "P" for the security level given when the user
"PASSES" or completes the verification process, and "F" for the
security level given to the user when he/she fails to complete the
verification process. A line in the security level configuration file
could look like this:
E5 P10 F3
This tells the door that a user coming into the door with a security
level of 5, should go out with a security level of 10 if he/she
successfully completes the verification process, or 3 if he/she fails to
be verified. The two exit numbers could just as easily have had a plus
sign or a minus sign to raise or lower the security level by that
amount. In that case, the line above would look like this:
E5 P+10 F-3
This would raise the verified users level by 10, and lower the
unverified users level by 3. This is a very powerful feature of TCCB,
and can be used among other things to limit the number of times a user
gets to run the door before being locked out. If the configuration file
looked like this:
E9 P10 F-1
E8 P10 F-1
E7 P10 F-1
E6 P10 F-1
E5 P10 F-1
E4 P10 F-1
E3 P10 F00
This file will allow a user who starts out with a level of 9 to try
the door 6 times and then if he fails on the 7th attempt he would be
set to a security level of 0 and be locked out!
This is just one of many things that can be done with this feature of
TCCB. Other ideas include triggering questionnaires at different
levels. This weeds out the "PROBLEM" users that can't make it through
the door and need assistance. Also users who start out with different
status on the system being set to a level that reflects that status
after being processed through the door, like visiting sysops.
Printer Output
--------------
A new feature as of version 1.06 is printer support. This
feature, when activated, will send the TCCB.LOG file data to the
standard BIOS printer device LPT1 or LPT2 etc. To activate the
printer simply put the printer port number as the last parameter on the
command line in the batch file. If this parameter is absent or is "0"
then the printer will be deactivated (turned off). For LPT1 put a "1"
in the last parameter of the batch file command line. For LPT2 put a
"2" and so on... If an error occurs while TCCB is sending data to the
printer or the printer fails to respond within 30-40 seconds then the
door will abandon sending data to the printer and return to normal
operation after displaying "Printer error!" on the local console. This
may cause a 30 to 40 second period during which TCCB will ignore
input from both remote and local consoles. After 30 to 40 seconds TCCB
will resume normal operation.
Sysop Functions
---------------
TCCB has several features of interest to the sysop. These are
available only from the local console. They are activated by single
hot keys. The functions and their respective hot keys are:
Shell to DOS <F5>
Prints a message to user then exits to dos. Type
"EXIT" to return to TCCB.
Return user to system (Close Door) <F8>
Toggle display On or Off <F9>
Chat mode <F10>
Clears the screen and displays the sysop's and the
users typeout, allowing the sysop to chat with
the user. Time restrictions are NOT suspended while
in chat mode.
Display status screen <ALT-H>
Toggles between status displays.
Errors Returned by TCCB
-----------------------
There are several fatal errors returned by TCCB. If you get one of
these you have either got faulty hardware or you have not set up the
batch file correctly. The errors are:
Batch file configuration parameters missing!
--------------------------------------------
TCCB was executed with NO parameters. Bad batch file.
Batch file has too few parameters!
----------------------------------
The TCCB command line had less then 11 parameters.
Batch file has too many parameters!
-----------------------------------
There were more then 12 parameters on the TCCB command line.
Can't open DORINFO#.DEF!
------------------------
Most likely the path to DOORINFO[node#].DEF is incorrect.
While reading DORINFO#.DEF!
---------------------------
A disk error has occurred wile reading DORINFO[node#].DEF
DOUT#.DEF write error!
----------------------
A disk error has occurred while TCCB was writing out the
DOUT[node#].DEF file.
Can't open VERIFIED.LOG!
------------------------
A disk error has occurred while accessing the VERIFIED.LOG file.
Can't open TCCB.LOG!
--------------------
A disk error has occurred while accessing the TCCB.LOG file.
Modem error during callback!
----------------------------
The result string returned by your modem does not match the BUSY
or CONNECT strings specified in the batch file.
Unsupported BBS type!
---------------------
You should never get this error unless you are trying to run the
door on a BBS other then RBBS. This version of TCCB will only
work with RBBS.
Bad port specification, must be PORTADDR:IRQ# or F:PORT#!
---------------------------------------------------------
Your port info in the batch file in incorrectly formatted.
Fossil Driver NOT found!
------------------------
The batch file is set up for a Fossil Driver when there is no
fossil driver loaded in memory.
Can't allocate Memory!
----------------------
A problem occurred while allocating memory. You may need more
memory, or remove some memory resident programs and try again.
Library error!
--------------
You should never get this error! If you get this error please
contact the authors for assistance.
Corrupted executable!
---------------------
The CB.EXE file has been corrupted. This could be due to disk
errors. Check your disk system. Unpack the CB.EXE file from the
distribution package again. If you still get this error, you
have a bad copy of TCCB. NOTE: this could be due to a computer
virus attacking the CB.EXE file.
Printer error!
--------------
The printer has been enabled but when TCCB attempted to send data
to it it got one of these errors:
1. Device timeout (no response within 30-40 seconds)
2. Paper out
3. I/O error (ports not configured correctly etc.)
If you have any problems installing the TCCB door, you may send a
message to the sysop of Frostbyte Falls BBS at 703-425-6640.
Author's Note
-------------
Many hours of coding and debugging have gone into TCCB. In addition
to the work of the authors, there have been contributions that deserve
more than the mention that they get here. We would like to express our
heartfelt thanks to the SysOps of the following BBSes who have helped
to test and improve TCCB and make it what it is today.
Joseph Aquino Jeff Alberts
SysOp of: SysOp of:
Ulysses Systems Network Helm's Deep
Rome, N. Y. Herndon, Va.
Main BETA test site First BETA test site
Other Things And Stuff We Forgot!
---------------------------------
Turbo C is a copyrighted product of Borland international.
Turbo Assembler is a copyrighted product of Borland International.
IBM is another word for ..
Pascal is a language I don't know!
My sweet pea has BLUE eyes (version 1.0).
TCCB stands for T.... C Call Back (door)
Now is the excellent foppery of the world that when we are sick in
fortune.
1966 VW's with no rust and 175 HP engines are FUN!
Some day I am going to put the cover back on my computer.
THANK YOU!